(bashdb): Prompt now included parenthesis for subshell

levels. Fix erroneous print expression command, and fix typos.
(perldb): Undo previous change in prompt regexp.

diff --git a/lisp/gud.el b/lisp/gud.el
index c24ccb027412d6accf7c399f60b78591cde35b23..e3c2c9f41bf6cf6e631f0eec4e3d7abe93c55270 100644 (file)
--- a/lisp/gud.el
+++ b/lisp/gud.el
@@ -1249,7 +1249,7 @@ and source-file directory for your debugger."
 ;  (gud-def gud-down   "down %p"      ">" "Down N stack frames (numeric arg).")
   (gud-def gud-print  "%e"           "\C-p" "Evaluate perl expression at point.")
 
-  (setq comint-prompt-regexp "^  DB<+(*[0-9])*+>+ ")
+  (setq comint-prompt-regexp "^  DB<+[0-9]+>+ ")
   (setq paragraph-start comint-prompt-regexp)
   (run-hooks 'perldb-mode-hook))
 \f
@@ -2123,12 +2123,12 @@ and source-file directory for your debugger."
   (gud-def gud-finish "finish"     "\C-f" "Finish executing current function.")
   (gud-def gud-up     "up %p"      "<" "Up N stack frames (numeric arg).")
   (gud-def gud-down   "down %p"    ">" "Down N stack frames (numeric arg).")
-  (gud-def gud-print  "pe %e"      "\C-p" "Evaluate bash expression at point.")
+  (gud-def gud-print  "x %e"      "\C-p" "Evaluate BASH expression at point.")
 
   ;; Is this right?
-  (gud-def gud-statement "eval %e" "\C-e" "Execute Python statement at point.")
+  (gud-def gud-statement "eval %e" "\C-e" "Execute BASH statement at point.")
 
-  (setq comint-prompt-regexp "^bashdb<+[0-9]*>+ ")
+  (setq comint-prompt-regexp "^bashdb<+(*[0-9]+)*>+ ")
   (setq paragraph-start comint-prompt-regexp)
   (run-hooks 'bashdb-mode-hook)
   )